Data Processing System

ABSTRACT

A data processing system being configured to select between different hardware resources for the running of an application configured for the sending and receiving of data over a network. The selection of hardware resources may be between resources on the network interface device, and hardware resources on the host. The selection of hardware resources may be between first and second hardware resources on the network interface device. An API is provided in the data processing system that responds to requests from the application irrespective of the hardware on which the application is executing.

BACKGROUND OF THE INVENTION Field

The present application relates to a method, apparatus, system andcomputer program. In particular, but not exclusively, the presentapplication relates to the selection and use of different hardwareresources of a data processing system for running an application.

BACKGROUND

Applications supported by, for example, host computing devices areconfigured to form application layer messages for transmission over anetwork. Such messages may be transmitted from the host computing deviceover a network using network interface devices. Similarly, messages maybe received at the host computing device from over a network using anetwork interface device.

Network interface devices typically provide an interface between thehost computing device and a network. The network interface device may beconfigured to process data which is received from the network and/orprocess data which is to be put on the network.

SUMMARY

According to a first aspect, there is provided a data processing systemcomprising: a host computing device comprising hardware resources; anetwork interface device arranged to couple the host computing device toa network, the network interface device comprising hardware resources;and an application configured to run on one or more of the hardwareresources of the data processing system, wherein the data processingsystem is configured to select between the hardware resources of thehost computing device and the hardware resources of the networkinterface device for running at least part of the application.

In one embodiment, the host computing device comprises an applicationprogramming interface configured to receive requests from theapplication to determine available hardware resources of the dataprocessing system.

In one embodiment, the data processing system is configured to selectbetween the hardware resources of the network interface device and thehardware resources of the host computing device in dependence upon atleast one of: system workload; availability of the hardware resources ofthe host computing device; and availability of the hardware resources ofthe network interface device.

In one embodiment, the data processing system comprises a runtimesupport for the application, wherein the runtime support is configuredto perform the selection between the hardware resources of the hostcomputing device and the hardware resources of the network interfacedevice for running the application.

In one embodiment, the runtime support comprises a virtual machineenvironment.

In one embodiment, the application is configured to at least one of:form a message for transmission over the network; and consume a messagereceived over the network.

According to a second aspect, there is provided a network interfacedevice arranged to couple the host computing device to a network, thenetwork interface device comprising first hardware resources and secondhardware resource, the network interface device comprising: anapplication configured to run on one or more of the hardware resourcesof the network interface device, wherein the network interface device isconfigured to select between the first and second hardware resources forrunning the application.

In one embodiment, the application is configured to make requests to anapplication programming interface of the host computing device todetermine available hardware resources of the data processing system.

In one embodiment, the network interface device is configured to selectbetween the first hardware resources and the second hardware resourcesin dependence upon at least one of: system workload; availability of thefirst hardware resources; and availability of the second hardwareresources.

In one embodiment, the network interface device comprises a runtimesupport for the application, wherein the runtime support is configuredto perform the selection between the first hardware resources and thesecond hardware resources.

In one embodiment, the runtime support comprises a virtual machineenvironment.

In one embodiment, the application is configured to at least one of:form a message for transmission over the network; and consume a messagereceived over the network.

According to a third aspect, there is provided a host computing devicecomprising: an interface to a network interface device arranged tocouple the host computing device to a network; and hardware resourcesconfigured to run an application, wherein the host computing device isconfigured to select between the hardware resources of the hostcomputing device and hardware resources of the network interface devicefor running the application.

According to a fourth aspect, there is provided a method comprising:selecting hardware resources for running an application, the selectionbeing made between hardware resources of a host computing device andhardware resources of a network interface device, wherein the networkinterface device is arranged to couple the host computing device to anetwork; and causing an application to run on the selected hardwareresources.

According to a fifth aspect, there is provided a method comprising:selecting hardware resources for running an application, the selectionbeing made between first hardware resources of the network interfacedevice and second hardware resources of the network interface device,wherein the network interface device is arranged to couple a hostcomputing device to a network; and causing an application to run on theselected hardware resources.

According to a sixth aspect, there is provided a method implemented in ahost computing device, the method comprising: selecting hardwareresources for running an application, the selection being made betweenhardware resources of the host computing device and hardware resourcesof a network interface device, wherein the network interface device isarranged to couple the host computing device to a network; and causingan application to run on the selected hardware resources.

According to a seventh aspect, there is provided a non-transitorycomputer readable medium encoded with instructions that when executed byone or more processors of a data processing system performs a method,the method comprising: selecting hardware resources for running anapplication, the selection being made between hardware resources of ahost computing device and hardware resources of a network interfacedevice, wherein the network interface device is arranged to couple thehost computing device to a network; and causing an application to run onthe selected hardware resources.

According to an eighth aspect, there is provided a non-transitorycomputer readable medium encoded with instructions that when executed byone or more processors of a network interface device performs a method,the method comprising: selecting hardware resources for running anapplication, the selection being made between first hardware resourcesof the network interface device and second hardware resources of thenetwork interface device, wherein the network interface device isarranged to couple a host computing device to a network; and causing anapplication to run on the selected hardware resources.

According to a ninth aspect, there is provided a non-transitory computerreadable medium encoded with instructions that when executed by one ormore processors of a host computing device performs a method, the methodcomprising: selecting hardware resources for running an application, theselection being made between hardware resources of the host computingdevice and hardware resources of a network interface device, wherein thenetwork interface device is arranged to couple the host computing deviceto a network; and causing an application to run on the selected hardwareresources.

According to an tenth aspect, there is provided a data processing systemcomprising: a host computing device comprising hardware resources; anetwork interface device arranged to couple the host computing device toa network, the network interface device comprising hardware resources;and an application programming interface configured to receive requestsfrom a first entity running on the hardware of the host computing deviceand a second entity running on the hardware of the network interfacedevice, wherein operations performed by the application programminginterface in response to the requests are independent of whether therequests are received from the first entity or the second entity.

In one embodiment, the first entity comprises a first application andthe second entity comprises a second application.

In one embodiment, the first entity and the second entity are differentinstances of an application.

In one embodiment, the first entity and the second entity each comprisecomponents of at least one runtime support.

In one embodiment, the requests comprise at least one of: requests foraccess to hardware resources on behalf of an application; and requestsfor an indication as to the availability of hardware resources of thedata processing system.

In one embodiment, responses to the requests provided by the applicationprogramming interface are independent of the hardware on which the firstentity and the second entity execute.

According to a eleventh aspect, there is provided a host computingdevice comprising: an interface to a network interface device arrangedto couple the host computing device to a network; hardware resourcesconfigured to run a first entity; and an application programminginterface configured to receive requests from the first entity and froma second entity running on the hardware of the network interface device,wherein operations performed by the application programming interface inresponse to the requests are independent of whether the requests arereceived from the first entity or the second entity.

According to a twelfth aspect, there is provided a method implemented ina data processing system, the method comprising: receiving at anapplication programming interface, a request from a first entityexecuting on hardware of a host computing device; receiving at theapplication programming interface, a request from a second entityexecuting on hardware of a network interface device; and the applicationprogramming interface performing operations in response to the requeststhat are independent of whether the requests are received from the firstentity or the second entity.

According to an thirteenth aspect, there is provided a methodimplemented in a host computing device, the method comprising: receivingat an application programming interface, a request from a first entityexecuting on hardware of the host computing device; receiving at theapplication programming interface, a request from a second entityexecuting on hardware of a network interface device; and the applicationprogramming interface performing operations in response to the requeststhat are independent of whether the requests are received from the firstentity or the second entity.

According to a fourteenth aspect, there is provided a non-transitorycomputer readable medium encoded with instructions that when executed byone or more processors of a data processing system performs a method,the method comprising: receiving at an application programminginterface, a request from a first entity executing on hardware of a hostcomputing device; receiving at the application programming interface, arequest from a second application executing on hardware of a networkinterface device; and the application programming interface performingoperations in response to the requests that are independent of whetherthe requests are received from the first entity or the second entity.

According to a fifteenth aspect, there is provided a non-transitorycomputer readable medium encoded with instructions that when executed byone or more processors of a host computing device performs a method, themethod comprising: receiving at an application programming interface, arequest from a first entity executing on hardware of the host computingdevice; receiving at the application programming interface, a requestfrom a second entity executing on hardware of a network interfacedevice; and the application programming interface performing operationsin response to the requests that are independent of whether the requestsare received from the first entity or the second entity.

According to a sixteenth aspect, there is provided a computer programcomprising instructions such that when the computer program is executedon a computing device provides a method according to any of: the fourthto sixth aspects, the twelfth aspect, and the thirteenth aspect.

BRIEF DESCRIPTION OF FIGURES

Some embodiments will now be described by way of example only withreference to the accompanying figures in which:

FIG. 1 shows a schematic view of a data processing system coupled to anetwork;

FIG. 2 shows a schematic view of a data processing system comprising anapplication configured to run on a host computing device and providedata for transmission over a network;

FIG. 3 shows a schematic view of a data processing system comprising aan application configured to run on a network interface device andprovide data for transmission over a network;

FIG. 4 shows a schematic view of a data processing system comprising anapplication configured to run on either a host computing device or anetwork interface device;

FIG. 5 shows a schematic view of a data processing system comprising anapplication configured to run on different hardware resources of anetwork interface device;

FIG. 6 shows an example of a method for selecting and using hardwareresources for running an application;

FIG. 7 shows a schematic view of a network interface device arranged tocouple a host computing device to a network;

FIG. 8 shows a schematic view of a data processing system comprising anapplication configured to run on a host computing device and receivedata from a network; and

FIG. 9 shows a schematic view of a data processing system comprising anapplication configured to run on a network interface device and receivedata from a network.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled inthe art to make and use one or more embodiments, and is provided in thecontext of particular examples. Various modifications to the disclosedembodiments will be readily apparent to those skilled in the art.

The general principles defined herein may be applied to otherembodiments and examples without departing from the spirit and scope ofthe present invention. Thus, the present invention is not intended to belimited to the embodiments shown, but is to be accorded the widest scopeconsistent with the principles and features disclosed herein.

When data is to be transferred between two data processing systems overa data channel, such as a network, one or both of the data processingsystems has a suitable network interface to allow it to communicateacross the channel. Often the network is based on Ethernet technology.Other embodiments may alternatively or additionally use othertechnology. Data processing systems that are to communicate over anetwork may be equipped with network interfaces that are capable ofsupporting the physical and logical requirements of the associatednetwork protocol. The physical hardware component of network interfacesmay be referred to as network interface devices or so called networkinterface cards (NICs).

Most computer systems include an operating system (OS) through whichuser level applications communicate with the network. A portion of theoperating system, sometimes referred to as the kernel, may have one ormore protocol stacks for protocol processing data to form data packetsfor transmission over the network and protocol processing data packetsreceived from the network. By providing these functions in the operatingsystem kernel, the complexities of and differences among networkinterface devices can be hidden from the user level application.Alternatively or additionally, the network hardware and other systemresources (such as memory) can be safely shared by many applications andthe system can be secured against faulty or malicious applications.

Some computer systems may comprise a plurality of guest operatingsystems managed by a hypervisor, with each guest operating systemsupporting multiple application endpoints having their own networkaddresses. Each of the applications may provide data to be communicatedover the network.

An example of a data processing system 100 for carrying out transmissionacross a network is shown in FIG. 1. The data processing system 100comprises a host computing device 101 coupled to a network interfacedevice 102 that is arranged to interface the host 101 to network 103.The host computing device 101 includes an operating system 104supporting one or more user level applications 105, The host computingdevice 101 may also include a network protocol stack 106. For example,the protocol stack 106 may be a component of the application 105, alibrary with which the application 105 is linked, or be provided by theoperating system 104. In some embodiments, more than one protocol stack106 may be provided.

The network protocol stack 106 may be a Transmission Control Protocol(TCP) stack. The application 105 can send and receive TCP/IP messages byopening a socket and reading and writing data to and from the socket,and the operating system 104 causes the messages to be transportedacross the network 103. For example, the application 105 can invoke asystem call (syscall) for transmission of data through the socket andthen via the operating system 104 to the network 103. This interface fortransmitting messages may be known as the message passing interface.

During operation of the data processing system 100, data to betransmitted onto the network 103 may be transferred from the hostcomputing device 101 to the network interface device 102 fortransmission. In one example, data packets may be transferred from thehost 101 to the network interface device 102 directly by the hostprocessor. The host 101 may provide data to one or more buffers 107located on the network interface device 102. The network interfacedevice 102 may then prepare the data packets and transmit them over thenetwork 103.

In the example data processing system 100, the application 105 that isresponsible for sending and receiving messages is located on the host101. However, in accordance with examples of the present application, anumber of different possible hardware resources may be used to providethe application. For example, the application may alternatively oradditionally be provided by a host central processing unit (CPU), by ahost graphical processing unit (GPU), by a host Intelligence ProcessingUnit (IPU), by a host Tensor Processing Unit (TPU), by a fieldprogrammable gate array (FPGA) logic present on a network interfacedevice, by an embedded CPU on a network interface device or by otherprocessing devices present on a host and/or on a network interfacedevice. FIGS. 2, 3, 4, 5, 8, and 9 illustrate examples of dataprocessing systems according to embodiments of the application. In someexamples, these data processing systems may comprise a host computingdevice having a single operating system. The protocol stack andapplication illustrated being capable of running on the single operatingsystem. In other embodiments, the data processing systems may havemultiple guest operating systems being managed by a hypervisor. In thiscase, there may be multiple applications configured to execute onseparate operating systems and being configured to send and receive dataover the network.

Reference is made to FIG. 2, which shows an example of a data processingsystem 200, having an application 210 configured to run on hardwareresources of the host computing device. Such hardware resources may beone or more processors, such as CPUs, GPUs, IPUs, and TPUs. The hostcomputing device also comprises a protocol stack 220 for performingprotocol processing and providing headers for data packets. The protocolstack 220 may comprise a protocol stack 220 configured to performtransport protocol processing of data. The protocol stack 220 maycomprise a TCP/IP protocol stack. The protocol processing performed bythe stack 220 may comprise transport protocol processing. The transportprotocol processing may be TCP/IP protocol processing. The protocolprocessing performed by the stack 220 may comprise some upper layerprocessing, such as iSCSI (Internet Small Computer Systems Interface) orNVME (Non-Volatile Memory Express) processing. The application 210 mayperform the remaining upper layer processing for a data packet (i.e. theapplication may complete the remaining upper processing layers). Thehost computing device also comprises an application programminginterface 230, by which the application 210 can communicate with theprotocol stack 220 by, for example, requesting headers for data packetsfor the transmission of messages over the network. The host computingdevice also comprises a transmit function 270, which is invoked by theapplication 210 to transmit data packets over the network. The transmitfunction 270 may a library, such as an Ether Fabric Virtual Interface(EFVI) and/or a Data Plane Development Kit (DPDK) library or a rawsocket.

FIG. 2 illustrates the steps that may be involved in the process oftransmitting data over the network. These steps are an example only. Inother examples, the order in which the steps are carried out may vary.

At step (i), the application 210 issues a request for one or moreheaders for the transmission of a data packet to the protocol stack 220through the API 230. In response, the protocol stack 220 provides theone or more headers 240 to the application 210. The protocol stack 220may provide the one or more headers 240 by writing the one or moreheaders 240 to a memory to which the application 210 has access. Theprotocol stack 220 may write the one or more headers to this memory bycompleting fields in an object passed as an argument to the API call.The application 210 forms an application layer message 250 fortransmission over the network.

At step (ii), the application 210 is configured to combine the one ormore headers 240 with the application layer message 250 to form a datapacket 260.

At step (iii), the application 210 is configured to invoke the transmitfunction 270 to cause the data packet 260 to be transmitted over thenetwork. The data packet 260 is passed to the network interface devicethat is coupled to the host computing device via the I/O bus 280. Thenetwork interface device is configured to transmit the data packet 260over the network.

At step (iv), the application 210 provides the transmitted frame to theprotocol stack 220 via the API 230. The protocol stack 220 performsprotocol processing for the transmitted data packet. The protocolprocessing performed by the stack 220 at step (iv) may comprisetransport protocol processing. The transport protocol processing maycomprise updating the state associated with a transport stream to whichthe transmitted data packet belongs. The transport protocol processingmay comprise TCP/IP protocol processing.

Hence, in the example described with respect to FIG. 2, the hardwareresources on which the application 210 executes, and hence which formthe application layer message are part of the host computing device. Thenetwork interface device, in this example, may be configured to performthe transmit operation only.

Reference is made to FIG. 8, which shows an example of a data processingsystem 800. The data processing system 800 may be the same as the dataprocessing system 200 illustrated in FIG. 2, and so like elements of thesystem 800 have been indicated with like elements of the system 200.FIG. 8 illustrates the steps that may be involved in the process ofreceiving data from over the network. These steps are an example only.In other examples, the order in which the steps are carried out mayvary.

A data packet 810 is received at the network interface device and iswritten to a receive buffer 840 in the network interface device. Anevent notification may be written to an event queue associated with thereceive buffer 840 to notify a processor of the host of the arrival ofthe data packet. The network interface device is configured to firstseparate the network and transport layers headers from the payload. Thenetwork interface device then writes the payload data into the receivebuffer. The network interface device may be configured to write thepayload data in byte stream order in dependence on the information (e.g.sequence number, etc) in the transport headers.

In some examples, if the receive buffer 840 contains in order datareceived from the network, then this is indicated to the application 210by the network interface device. In response to receiving the indicationthat the receive buffer 840 contains in order data, the application 210may process the in order data prior to transport processing beingperformed by the protocol stack 220. In some examples, if the receivebuffer 840 contains out of order data, the application 210 may deferprocessing of the data, until corresponding in order data is available.The in order data may be received in the receive buffer 840 via aretransmission over the network.

In some examples, if the receive buffer 840 contains data which haspassed one or more transport layer validity checks (e.g. a checksum)then this is indicated to the application 210. In response to receivingthe indication that data in the receive buffer 840 passes the one ormore transport layer validity checks, the application 210 may processthe data having passed said one or more validity checks prior totransport processing being performed by the protocol stack 220. In someexamples, if the receive buffer 840 contains data failing the one ormore validity checks, the application 210 may defer processing of thedata, until corresponding data which passes the one or more validitychecks is available. The data passing the one or more validity checksmay be received in the receive buffer 840 via a retransmission over thenetwork.

The application 210 can determine to process one or more of: out oforder data, bad data (data contain errors), or data with missing regionsthat is held in the receive buffer 840. Alternatively, the application210 may wait for in order, correct data (which may require aretransmission from over the network) to be received from over thenetwork.

Therefore, the application 210 receives the payload/application layermessage from the receive buffer 840 in the network interface device. Theapplication 210 can consume the application layer message. Additionallyor alternatively, a copy of the payload/application layer message can beprovided to the application component 850 executing on the networkinterface device. The runtime support (not shown in FIG. 8) determineswhether the payload is delivered to the application 210 on the host, theapplication component 850 on the network interface device, or to both ofthem. The runtime support may make such a determination separately fordifferent data flows. In other words, the determination may be made on aper flow basis.

The network interface device delivers the headers 820 and, optionally,the entire data packet 810 to the protocol stack 220. If only theheaders 820 are delivered to the protocol stack 220, then the networkinterface device performs one or more validity checks (e.g. checksumcalculations) for the data packet 810 and provides an indication of theresults of the one or more validity checks to the protocol stack 220.

The protocol stack 220 performs protocol processing of the data packet810. The protocol stack 220 may perform transport processing for thedata packet 810. The transport protocol processing may be TCP/IPprotocol processing. The protocol processing performed by the stack 220may comprise at least some upper layer processing, such as iSCSI(Internet Small Computer Systems Interface) or NVME (Non-Volatile MemoryExpress) processing.

The protocol processing may produce a message that is to be sent overthe network. In response to the protocol processing, the data processingsystem may produce and transmit the message over the network. Themessage may be an acknowledgment message (e.g. a TCP ACK). The messagecould contain information from which the transmitting protocol stackcould infer one of: an acknowledgment of the received data packet 810,an instruction to change the protocol window size, an instruction toadjust the transmission rates, a request for retransmission of some orall of the data. The message represents the result of the receiveprocessing of the data packet 810.

The application code which is causing the connection to occur is on thehost processing device. However in embodiments, a component 850 of theapplication 210 is provided in the network interface device. The message(e.g. an acknowledgment message) that is produced as a result of theprotocol processing (and transmitted over the network) is providedthough the API 230 to the application component 850 on the networkinterface device. The application component 850 can modify this messagewhich is to be transmitted over the network. For example, if theapplication 210 is configured to process the data irrespective ofwhether or not it passes a validity check, e.g. if the application 210doesn't require data which it receives to be in order, and is configuredto process it regardless, then the application component can change amessage requesting retransmission (e.g. a NACK/negative acknowledgment)message to a message that does not request retransmission (e.g. anACK/acknowledgement) such that no retransmission is requested. Theapplication component 850 may convert a NACK to an ACK, with the ACKthen being transmitted over the network to the sender of the datapacket. The runtime support may determine whether an NACK messagereceived at the application component 850 is to be modified. The runtimesupport may determine that NACKs are to be converted to ACKs if it isdetermined that the application 210 is configured to process out oforder data. More broadly, the runtime support may be configured todetermine whether and how the application component 850 may modifymessages received from the protocol stack 220 as a result of theprotocol processing of the headers 820.

The runtime support is provided as the runtime support for theapplication irrespective of the hardware (e.g. on the network interfacedevice or the host) on which the application executes. The runtimesupport is also provided as the runtime support for separate componentsof the application 210, e.g. application component 850.

The protocol stack 220 may also be configured to provide at least partof the payload of the data packet 810 to the application component 850.In some examples, the application component 850 is configured to processthe data after it was been protocol processed by the protocol stack 220.In other examples, the application component 850 may not wait forprotocol processing to complete, but may pre-process the data.

Reference is made to FIG. 3, which shows an example of a data processingsystem 300, having an application 310 configured to run on hardwareresources of the network interface device. Such hardware resources maybe one or more processors, such as FPGA logic, or one or more embeddedCPUs. The host computing device comprises a protocol stack 320, such asa TCP/IP protocol stack, for performing protocol processing andproviding headers 340 for data packets. The host computing device alsocomprises an application programming interface 330, by which theapplication 310 can communicate with the protocol stack 320 by, forexample, requesting headers 340 for data packets for the transmission ofmessages over the network. The protocol stack 320 may comprise aprotocol stack 320 configured to perform transport protocol processingof data. The protocol stack 320 may comprise a TCP/IP protocol stack.Although the protocol stack 320 is shown as being part of the hostcomputing device, in some examples, the protocol stack 320 may beprovided on the network interface device. The protocol stack 320 may beconfigured to run on an embedded CPU of the network interface device.The protocol processing performed by the stack 320 may comprisetransport protocol processing. The transport protocol processing may beTCP/IP protocol processing. The protocol processing performed by thestack 320 may comprise upper layer processing, such as iSCSI or NVMEprocessing. The application 310 may perform the remaining upper layerprocessing for a data packet (i.e. the application may complete theremaining upper processing layers). The network interface devicecomprises a transmit function 370, which is invoked by the application310 to transmit data packets over the network. The transmit function 370may a library, such as an EFVI and/or DPDK or a raw socket. The transmitfunction 370 may be provided by an embedded CPU or a hardware API of thenetwork interface device. The host computing device and the networkinterface device are configured to communicate with one another over theI/O Bus 380. FIG. 3 illustrates the steps that may be involved in theprocess of transmitting data over the network. These steps are anexample only. In other examples, the order in which the steps arecarried out may vary.

At step (i), the application 310 issues a request for one or moreheaders for the transmission of a data packet to the protocol stack 320through the API 330. In response, the protocol stack 320 provides theone or more headers 340 to the application 310. The protocol stack 320may provide the one or more headers 340 by writing the one or moreheaders 340 to a memory to which the application 310 has access. Theapplication 310 also forms an application layer message 350 fortransmission over the network. The application 310 may perform upperlayer protocol processing when forming the application layer message350.

At step (ii), the application 310 is configured to combine the one ormore headers 340 with the application layer message 350 to form a datapacket 360.

At step (iii), the application 310 is configured to invoke the transmitfunction 370 to cause the data packet 360 to be transmitted over thenetwork. The transmit function 370 is configured to transmit the datapacket 360 over the network.

At step (iv), the protocol stack 320 then performs protocol processingfor the transmitted data packet. The protocol processing performed bythe stack 320 at step (iv) may comprise transport protocol processing.The transport protocol processing may comprise updating the stateassociated with a transport stream to which the transmitted data packetbelongs. The transport protocol processing may comprise TCP/IP protocolprocessing.

Hence, in the example described with respect to FIG. 3, the hardwareresources on which the application 310 executes and hence, which formthe application layer message are present on the network interfacedevice. However, the application 310 is able to access, the hostprotocol stack 320 via the API 330.

Reference is made to FIG. 9, which shows an example of a data processingsystem 900. The data processing system 900 may be the same as the dataprocessing system 300 illustrated in FIG. 3, and so like elements of thesystem 900 have been indicated with like elements of the system 300.FIG. 9 illustrates the steps that may be involved in the process ofreceiving data from over the network. These steps are an example only.In other examples, the order in which the steps are carried out mayvary.

A data packet 910 is received at the network interface device and iswritten to a receive buffer 940 in the network interface device. Anevent notification may be written to an event queue associated with thereceive buffer 940 to notify a processor of the host of the arrival ofthe data packet. The network interface device is configured to firstseparate the network and transport layers headers from the payload. Thenetwork interface device then writes the payload data into the receivebuffer 940. The network interface device may be configured to write thepayload data in byte stream order in dependence on the information (e.g.sequence number, etc) in the transport headers.

In some examples, if the receive buffer 940 contains in order datareceived from the network, then this is indicated to the application 310by the network interface device. In response to receiving the indicationthat the receive buffer 940 contains in order data, the application 310may process the in order data prior to transport processing beingperformed by the protocol stack 320. In some examples, if the receivebuffer 940 contains out of order data, the application 310 may deferprocessing of the data, until corresponding in order data is available.The in order data may be received in the receive buffer 940 via aretransmission over the network.

In some examples, if the receive buffer 940 contains data which haspassed one or more transport layer validity checks (e.g. a checksum)then this is indicated to the application 310. In response to receivingthe indication that data in the receive buffer 940 passes the one ormore transport layer validity checks, the application 310 may processthe data having passed said one or more validity checks prior totransport processing being performed by the protocol stack 320. In someexamples, if the receive buffer 940 contains data failing one or morevalidity checks, the application 310 may defer processing of the data,until corresponding data which passes the one or more validity checks isavailable. The data passing the one or more validity checks may bereceived in the receive buffer 940 via a retransmission from over thenetwork.

The application 310 can determine to process one or more of: out oforder data, bad data, or data with missing regions that is held in thereceive buffer 940. Alternatively, the application 310 may wait for inorder, correct data (which may require a retransmission from over thenetwork) to be received from over the network.

Therefore, the application 310 receives the payload/application layermessage from the receive buffer 940 in the network interface device. Theapplication 310 can consume the application layer message.

The network interface device delivers the headers 920 and, optionally,the entire data packet 910 to the protocol stack 320. If only theheaders 920 are delivered to the protocol stack 320, then the networkinterface device performs one or more validity checks (e.g. checksumcalculations) for the data packet 910 and provides an indication of theresults of the one or more validity checks to the protocol stack 320.

The protocol stack 320 performs protocol processing of the data packet910. The protocol stack 320 may perform transport processing for thedata packet 910. The transport protocol processing may be TCP/IPprotocol processing. The protocol processing performed by the stack 320may comprise at least some upper layer processing, such as iSCSI(Internet Small Computer Systems Interface) or NVME (Non-Volatile MemoryExpress) processing.

The protocol processing may produce a message that is to be sent overthe network. In response to the protocol processing, the data processingsystem may produce and transmit the message over the network. Themessage may be an acknowledgment message (e.g. a TCP ACK). The messagecould contain information from the which transmitting protocol stackcould infer one of: an acknowledgment of the received data packet 910,an instruction to change the protocol window size, an instruction toadjust the transmission rates, a request for retransmission of some orall of the data. The message represents the result of the receiveprocessing of the data packet 910.

The message produced as a result of the protocol processing (andtransmitted over the network) may be provided though the API 330 to theapplication 310 on the network interface device. The application 310 canmodify any message which is to be transmitted over the network. Forexample, if the application 310 is configured to process the datairrespective of whether or not it passes a validity check, e.g. if theapplication 310 doesn't require data which it receives to be in order,and is configured to process it regardless, then the application 310 canchange a message requesting retransmission (e.g. a NACK/negativeacknowledgment) message to a message that does not requestretransmission (e.g. an ACK/acknowledgement) such that no retransmissionis requested. The application 310 may convert a NACK to an ACK, with theACK then being transmitted over the network to the sender of the datapacket. The runtime support may determine whether an NACK messagereceived at the application 310 is to be modified. The runtime supportmay determine that NACKs are to be converted to ACKs if it is determinedthat the application 310 is configured to process out of order data.More broadly, the runtime support may be configured to determine whetherand how the application 310 may modify messages received from theprotocol stack 320 as a result of the protocol processing of the headers920.

The protocol stack 320 may also be configured to provide at least partof the payload of the data packet 910 to the application 310. In someexamples, the application 310 is configured to process the data after itwas been protocol processed by the protocol stack 320. In otherexamples, the application 310 may not wait for protocol processing tocomplete, but may pre-process the data.

Therefore, as illustrated by FIGS. 2, 3, 8, and 9, for both transmit andreceive processing, there is a plurality of different possibilities asregards to the hardware of a data processing system on whichapplications may run.

In accordance with examples of the application, a dynamic selectionbetween the hardware resources of the data processing system on whichthe application executes may be carried out. The application may beexpressed in a language with runtime support (i.e. having a runtimesystem). In some examples, the runtime support may perform the selectionas to the hardware resources on which the application is to execute. Thehardware resources may be predetermined on the basis of a staticanalysis. The data processing determines in dependence upon the systemworkload and availability of different hardware resources, appropriatehardware resources on which the application is to execute. For example,the data processing system may be configured to dynamically instantiateor move the application between one of more of: a host CPU, FPGA logicon the network interface device, an embedded CPU on the networkinterface device, a GPU on the host computing device, and an IPU/TPU onthe host computing device. This selection of hardware resources could becarried out by the host computing device, the network interface deviceor a combination of the two.

The runtime support (or runtime system) may be understood to be theenvironment in which a program running a particular language executes.The runtime support may provide a list of callable functions toapplications written in a particular programming language. Additionallyor alternatively, the runtime support may provide dynamic functions thatdo not need to be called by the application, such as memory managementor selection of hardware resources on which the application operates.

In examples of the application, the runtime support may run on the hostcomputing device and/or the network interface device. The runtimesupport may divided into different components, with different componentsbeing configured to execute on different hardware of the data processingsystem. For example, one or more components may be configured to executeon the host computing device and one or more components may beconfigured to execute on the network interface device.

Where the runtime support selects the hardware resources to be used forrunning the application, the runtime support may issue a request to theoperating system. The runtime support may issue requests to theoperating system of the host computing device via an API for access tohardware resources of the data processing system on behalf of theapplication. The operating system is configured to grant access to thehardware of the data processing system in response to the request. TheAPI may respond to the requests from the operating system independentlyof whether they are received from a component of the runtime supportrunning on the network interface device or a component of the networkinterface device running on the host computing device.

The selection of the hardware resources that is performed by the runtimesupport may be predetermined. The data processing system may store adata structure indicating to the runtime support, hardware that is to beused for the processing of the application. The runtime support mayselect the hardware resources to be used for running the application independence upon the data structure. The runtime support may then issue arequest to the operating system for access to the hardware resources independence on the indication in the data structure.

The selection of the hardware resources that is performed by the runtimesupport may be performed based on an analysis of the code of theapplication carried out by the runtime support. The runtime support mayanalyse the functions called in the code of the application and selecthardware based on a determination of the appropriate hardware forexecuting these functions.

The selection of the hardware resources that is performed by the runtimesupport may be performed based on an analysis of the running of theapplication. For example, the runtime support may analyse theperformance characteristics of the application when running on hardware,and update the selection of the hardware on which the application is torun on the basis of this analysis. The runtime support may analyse theperformance of the application when running on a first hardware orsecond hardware of the data processing system and, in response,determine to modify the selection of the hardware on which theapplication is to run, e.g. to cause the execution of the application tomove to the other of the first hardware or the second hardware.

In any case, when the runtime support has made a selection of hardwareon which the application is configured to run, the runtime support mayissue a request to the operating system via the API to request use ofthe selected hardware resources for execution by the application. Theruntime support may be configured to compile the application code to runon the selected hardware. The application may then run on the selectedhardware.

Reference is made to FIG. 4, which illustrates how, in accordance withexamples of the application, a dynamic selection between the hardwareresources of the data processing system on which the applicationexecutes may be carried out.

FIG. 4 shows a data processing system in which the application 410/420may execute in either hardware of the host computing device or hardwareof the network interface device. An instance 410 of the application maybe configured to run on hardware resources of the host computing device.An instance 420 of the application may be configured to run on thehardware resources on the network interface device. The data processingsystem may be configured to select between the hardware resources of thehost and the hardware resources of the network interface device for therunning of the application 410/420 and cause the application 410/420 torun on the selected resources. This selection may be carried out by theruntime support 470 for the application 410/420.

In the following description of FIG. 4 (and in the description of theremaining figures), the runtime support 470 is an example, and thefunctions (e.g. selection of hardware resources) described as beingcarried out by the runtime support 470 may in other examples, be carriedout by other elements of the data processing. For example, the dataprocessing system may select one or more hardware resources forexecuting the application 410/420 based on a data structure stored inthe memory of the data processing system.

The application 410/420 may be expressed a language, such as OpenCL, P4,Verilog, VHDL, C, C++, Java, or a library/toolkit or developmentenvironment such as SDAccel. In some examples, the application 410/420may be unaware of the particular runtime environment 470 on which theapplication 410/420 is executing. Use of the API 430 and/or the transmitfunction 440/450 may be abstracted by the runtime environment 470.

In some examples, the application 410/420 may issues calls to the API430 and transmit function 440/450, but have no dependency upon where theinstances of these functions are executed. Similarly the application mayissue calls to cause receive protocol processing by the protocol stack460 to be carried out, but have no dependency upon where the instancesof the API 430 and the protocol stack 460 are executed.

The runtime support 470 may issue requests for access to the hardwareresources to the operating system via the API 430.

An instance of the transmit function 440 may be provided in the networkinterface device to transmit data packets in response to a call from theapplication 420 running on the hardware resources of the networkinterface device. An instance of the transmit function 450 may beprovided in the host computing device to transmit data packets inresponse to call from the application 410 running on the hardwareresources of the host computing device.

If the application 410 executes on the hardware resources of the hostcomputing device, data may be transmitted over the network in accordancewith the steps described above with respect to FIG. 2. If theapplication 420 executes on the hardware resources of the networkinterface device, data may be transmitted over the network in accordancewith the steps described above with respect to FIG. 3. The protocolstack 460 may run on the host and perform protocol processing andprovide headers for data packets to application 410/420, irrespective ofthe hardware on which the application 410/420 is executing.

If the application 410 executes on the hardware resources of the hostcomputing device, data may be received from over the network andprocessed in accordance with the steps described above with respect toFIG. 8. If the application 420 executes on the hardware resources of thenetwork interface device, data may be received from over the network inaccordance with the steps described above with respect to FIG. 9.

Although the protocol stack 460 is shown as being part of the hostcomputing device, in some examples, the protocol stack may be providedon the network interface device. For example, protocol stacks for someprotocols (such as an RDMA) may execute on the network interface device.The protocol stack may be configured to run on an embedded CPU of thenetwork interface device. Such a protocol stack may execute in a hostCPU or in hard logic. The operation of such a protocol stack may betransparent to the application.

The API 430 may be a common API that can be accessed and used by theapplication 410/420 irrespective of whether the application 410/420executes on the hardware resources of the host computing device or onthe hardware resources of the network interface device. The API 430could be a standard API, such as the POSIX socket API. The run time mayperform the offload of Tx/Rx functions where appropriate. Additionallyor alternatively, the Tx/Rx functions may be performed by other software(e.g. on a CPU) in the host computing device and/or network interfacedevice. The API 430 may be used to determine available hardwareresources. The runtime support 470 may request an indication ofavailable hardware resources from the API 430, which may provide saidindication. The API 430 may be configured to determine availablehardware resources on the host computing device and on the networkinterface device.

The API 430 could be any object or abstraction within a library orimplemented within the runtime environment of the application. The API430 could be a component of a virtual-machine or other sandbox orinterpreted environments.

The runtime support 470 may be configured to select between hardwareresources on the host computing device, and hardware resources on thenetwork interface device for executing the application 410/420. Forexample, the runtime support 470 may select between a CPU of the host,and an FPGA of the network interface device and cause the application410/420 to run on one of these. The runtime support 470 may beconfigured to select between the hardware resources on the hostcomputing device, and hardware resources on the network interface devicein dependence upon the available resources on the host and networkinterface device and the suitability of the available resources giventhe application's requirements The selection of the resources can bemade based on static analysis of the application, on-fly observation ofthe application's behaviour, analysis of previous execution traces ofthe application, or static configuration.

Additionally or alternatively, the runtime support 470 may be configuredto select between different hardware resources of the network interfacedevice for executing the application. For example, the runtime support470 may select between an embedded CPU of the network interface deviceand an FPGA of the network interface device and cause the application torun on one of these.

Reference is made to FIG. 5, which illustrates in more detail an examplein which a selection between different hardware resources on the networkinterface device is made. It would be appreciated by the skilled personthat the selection of hardware resources on the network interface devicemay be combined with the selection between hardware resources on thehost and hardware resources on the network interface device asillustrated in FIG. 4.

One instance 510 of the application may be configured to execute onfirst hardware resources of the network interface device, whist anotherinstance 520 of the application may be configured to execute on secondhardware resources of the network interface device. The runtime support530 for the application 510/520 may be configured to select between thefirst hardware resources and the second hardware resources for therunning of the application 510/520 and cause the application 510/520 torun on the selected resources.

The application 510/520 may be expressed in a language, such as OpenCL,P4, Verilog, VHDL, C, C++, Java, or a library/toolkit or developmentenvironment such as SDAccel. In some examples, the application 510/520may be unaware of the particular runtime environment 530 on which theapplication 510/520 is executing. Use of the API 540 and transmitfunction 550 may be abstracted by the runtime environment 530. In someexamples, the application 510/520 may issues calls to the API 540 andtransmit function 550, but have no dependency upon where the instancesof these functions are executed. Similarly the application 510/520 mayissue calls to cause receive protocol processing by the protocol stack560 to be carried out, but have no dependency upon where the instancesof the API 540 and the protocol stack 560 are executed.

The runtime support 530 may issue requests for access to the hardwareresources to the operating system via the API 430.

An instance of the transmit function 550 may be provided in the networkinterface device to transmit data packets in response to a call from theapplication 510/520 running on the first or second hardware resources ofthe network interface device.

Application layer data may be formed by the application 510/520 andtransmitted over the network in accordance with the steps describedabove with respect to FIG. 3. The protocol stack 560 may run on the hostand perform protocol processing and provide headers for data packets toapplication 510/520, irrespective of the hardware on which theapplication 510/520 is executing.

Application layer data may be received from over the network andconsumed by the application 510/520 in accordance with the stepsdescribed above with respect to FIG. 9.

Although the protocol stack 560 is shown as being part of the hostcomputing device, in some examples, the protocol stack 560 may beprovided on the network interface device. The protocol stack 560 may beconfigured to run on an embedded CPU of the network interface device.

The API 540 may be a common API that can be accessed and used by theapplication 510/520, irrespective of whether the application 510/520executes on the first hardware resources or the second hardwareresources. The API 540 may be used to determine available hardwareresources. The runtime support 530 may request an indication ofavailable hardware resources from the API 540, which may provide saidindication. The API 540 may be configured to determine availablehardware resources on the network interface device. For example, the API540 may be configured to determine that the network interface devicecomprises an embedded CPU and a FPGA on which the application mayexecute.

The runtime support 530 may be configured to select between the firsthardware resources and the second hardware resources for executing theapplication 510/520. For example, the runtime support 530 may selectbetween an embedded CPU of the network interface device and an FPGA ofthe network interface device and cause the application 510/520 to run onone of these. The runtime support 530 may be configured to selectbetween the first hardware resources and the second hardware resourcesin dependence upon the availability of these resources and/or thesuitability of the resources for running the application. The selectionof the resources can be made based on static analysis of theapplication, on-fly observation of the application's behaviour, analysisof previous execution traces of the application, and/or staticconfiguration

Reference is made to FIG. 6, which illustrates an example method 600that may be implemented in a data processing system according toexamples of the application. It would be appreciated by the skilledperson that not all of the steps in the method are essential and that,in some examples one or more steps may be omitted.

At S610, the runtime support for the application requests an indicationof the available hardware resources in the data processing system forrunning the application from the API. The runtime support may beprovided by the host computing device and/or the network interfacedevice.

At S620, the API determines the available hardware resources. The APIthen provides an indication of the available hardware resources to theruntime support. The indication of available hardware resources maycomprise an indication of the available hardware resources on the hostcomputing device, and/or an indication of the available hardwareresources on the network interface device. Additionally oralternatively, the indication of available hardware resources maycomprise an indication of the availability of first and second hardwareresources on the network interface device.

The indication of the available hardware resources provided at S620 maycomprise an indication of the availability of the functionality providedby the hardware. The indication of the availability of may be anindication of accelerator block availability and suitability. Forexample, the indication may comprise an indication as to theavailability in the hardware of one or more of: cryptographic processingblocks, video processing blocks, machine learning acceleration blocks.

The API may allow the composition of a pipeline of accelerator blocks tobe constructed by the runtime support. This may allow additionalprotocol layers to be more efficiently processed. For example, transportlayer security (TLS) processing may be accomplished by pipelining theTCP processing acceleration with hardware encryption/decryptionresources. Similarly, for video codecs and compression, TCP processingacceleration may be pipelined with processing resources.

At S630, the runtime support selects hardware resources for running theapplication. The runtime support may select the hardware resources independence upon the indication provided by the API. The runtime supportmay select between hardware resources on the network interface deviceand hardware resources on the host computing device. Additionally oralternatively, the runtime support may select between first hardwareresources on the network interface device and second hardware resourceson the host computing device.

The selection of the hardware resources for running the application thatis made at S630 may be performed in dependence upon the availability ofthe functionality (e.g. the availability of accelerator blocks) providedby the hardware. For example, if the application is required to performvideo processing, and it is determined that the network interface devicecomprises hardware (e.g. an FPGA) having a video processing acceleratorblock, the runtime support may determine that the application is to runon the appropriate hardware of the network interface device thatincludes this video processing accelerator block.

The selection of the hardware resources performed at S630, may alsodepend upon the degree to which the application algorithm can beparallelised in FSM (finite state machines). This may be in contrast toexecution as a sequential instruction stream on a CPU/GPU/TPU. Forexample, if there is a high degree to which the application can beparallelised, the runtime support may select a GPU of the host computingdevice for executing the application. Alternatively, if there is a lowdegree to which the application can be parallelised, the runtime supportmay select an embedded CPU of the network interface device for executingthe application.

At S640, the application runs on the selected resources. The applicationmay run on the selected resources indicated to it by the runtimesupport. The runtime support may issue a request to the operating systemon behalf of the application to request use of the selected hardwareresources for executing the application.

The application may provide application layer messages for transmissionover the network. The application may receive application layer messagesfrom the network.

It should be understood that each block of the flowchart of FIG. 6, andany combination thereof may be implemented by various means or theircombinations, such as hardware, software, firmware, one or moreprocessors and/or circuitry.

Reference is made to FIG. 7, which shows an example of a networkinterface device 700 according to examples of the application in moredetail.

The network interface device 700 is arranged to couple the hostcomputing device 705 to the network 710. The network interface devicecomprises first hardware resources 715. The first hardware resources 715are shown as an FPGA in the example of FIG. 7, but may be a differenttype of hardware. The network interface device comprises second hardwareresources 725. The second hardware resources 725 comprise an embeddedCPU. The application 720 may be configured to run on the first hardwareresources 715. The application 720 may, therefore, be an FPGAapplication 715. Additionally or alternatively, the application 730 maybe configured to run on the second hardware resources 725.

The network interface device 700 may comprise a transport engine 730,configured to process the data packets in accordance with a transportprotocol, such as TCP/IP. The transport engine 730 may comprise aprotocol stack. The transport engine 730 may comprise a plurality ofslices or data pipeline, some of the slices being RX slices configuredto perform receive processing of the ingress data packets received fromthe network 710, and some of the slices being TX slices configured toperform transmit processing of the egress data packets to be transmittedonto the network 710. In some embodiments, a slice may be able to handleboth data to be transmitted and received data. Each slice may comprise,for example, an application specification integrated circuit (ASIC) oran FPGA.

In some examples, the transport engine 730 may be omitted, with theprotocol processing being performed by the host computing device asexplained with reference to FIGS. 2 and 3.

The network interface device 700 may comprise a first interface 735configured to receive data from the host 705 and pass data to the host705. The first interface 735 may be a fabric interface. The firstinterface 735 may interface the transport engine 730 with the hostcomputing device 705. Additionally or alternatively, the first interface735 may interface the application 720/730 running on the first 715and/or second 725 hardware resources with the host. The first interface735 may provide an application programming interface, allowing the host705 to perform memory read and writes to memory associated with theapplication 720/730.

The network interface device 700 may also comprise a second interface740 configured to interface the transport engine 730 with the network710 and configured to interface the application 720/730 with the network710. The second interface 740 may be a layer 2 streaming interface. Thesecond interface 740 may provide an interface to the network 710 via athird interface 745. The third interface 745 may receive data packetsfrom the second interface 740 and cause them to be transmitted over thenetwork 710. The third interface 745 may similarly receive data packetsfrom the network 710 and pass them to the second interface 740. Thethird interface 745 may comprise a MAC interface. The third interface745 may comprise a plurality of MAC interfaces. The third interface 745may comprise one or more Physical Coding Sublayer (PCS) interfaces. Thethird interface 745 may comprise one or more Physical Medium Attachment(PMA) interfaces.

The first interface is configured to allow the application 720/730 toreceive frames from the host 705. The application 720/730 may be able totransmit frames to the work with data path processing at the samebandwidth as the host PCI.

The layer 2 streaming interface is configure to allow the application720/730 to receive frames form any active MAC layer interface and totransmit frames to a data path associated with that MAC.

CLAUSES

The following clauses describe aspects of various examples of methodsrelating to aspects of the invention:

Clause 13. A host computing device comprising:

an interface to a network interface device arranged to couple the hostcomputing device to a network; and

hardware resources configured to run an application,

wherein the host computing device is configured to select between thehardware resources of the host computing device and hardware resourcesof the network interface device for running the application.

Clause 14. A method implemented in a data processing system, the methodcomprising:

selecting hardware resources for running an application, the selectionbeing made between hardware resources of a host computing device andhardware resources of a network interface device, wherein the networkinterface device is arranged to couple the host computing device to anetwork; and

causing an application to run on the selected hardware resources.

Clause 15. A method implemented in a network interface device, themethod comprising:

selecting hardware resources for running an application, the selectionbeing made between first hardware resources of the network interfacedevice and second hardware resources of the network interface device,wherein the network interface device is arranged to couple a hostcomputing device to a network; and causing an application to run on theselected hardware resources.

Clause 16. A method implemented in a host computing device, the methodcomprising:

selecting hardware resources for running an application, the selectionbeing made between hardware resources of the host computing device andhardware resources of a network interface device, wherein the networkinterface device is arranged to couple the host computing device to anetwork; and

causing an application to run on the selected hardware resources.

Clause 17. A non-transitory computer readable medium encoded withinstructions that when executed by one or more processors of a dataprocessing system performs a method, the method comprising:

selecting hardware resources for running an application, the selectionbeing made between hardware resources of a host computing device andhardware resources of a network interface device, wherein the networkinterface device is arranged to couple the host computing device to anetwork; and

causing an application to run on the selected hardware resources.

Clause 18. A non-transitory computer readable medium encoded withinstructions that when executed by one or more processors of a networkinterface device performs a method, the method comprising:

selecting hardware resources for running an application, the selectionbeing made between first hardware resources of the network interfacedevice and second hardware resources of the network interface device,wherein the network interface device is arranged to couple a hostcomputing device to a network; and

causing an application to run on the selected hardware resources.

Clause 19. A non-transitory computer readable medium encoded withinstructions that when executed by one or more processors of a hostcomputing device performs a method, the method comprising:

selecting hardware resources for running an application, the selectionbeing made between hardware resources of the host computing device andhardware resources of a network interface device, wherein the networkinterface device is arranged to couple the host computing device to anetwork; and

causing an application to run on the selected hardware resources.

Clause 26. A host computing device comprising:

an interface to a network interface device arranged to couple the hostcomputing device to a network;

hardware resources configured to run a first entity; and

an application programming interface configured to receive requests fromthe first entity and from a second entity running on the hardware of thenetwork interface device,

wherein operations performed by the application programming interface inresponse to the requests are independent of whether the requests arereceived from the first entity or the second entity.

Clause 27. A method implemented in a data processing system, the methodcomprising:

receiving at an application programming interface, a request from afirst entity executing on hardware of a host computing device;

receiving at the application programming interface, a request from asecond entity executing on hardware of a network interface device; and

the application programming interface performing operations in responseto the requests that are independent of whether the requests arereceived from the first entity or the second entity.

Clause 28. A method implemented in a host computing device, the methodcomprising:

receiving at an application programming interface, a request from afirst entity executing on hardware of the host computing device;

receiving at the application programming interface, a request from asecond entity executing on hardware of a network interface device; and

the application programming interface performing operations in responseto the requests that are independent of whether the requests arereceived from the first entity or the second entity.

Clause 29. A non-transitory computer readable medium encoded withinstructions that when executed by one or more processors of a dataprocessing system performs a method, the method comprising:

receiving at an application programming interface, a request from afirst entity executing on hardware of a host computing device;

receiving at the application programming interface, a request from asecond application executing on hardware of a network interface device;and

the application programming interface performing operations in responseto the requests that are independent of whether the requests arereceived from the first entity or the second entity.

Clause 30. A non-transitory computer readable medium encoded withinstructions that when executed by one or more processors of a hostcomputing device performs a method, the method comprising:

receiving at an application programming interface, a request from afirst entity executing on hardware of the host computing device;

receiving at the application programming interface, a request from asecond entity executing on hardware of a network interface device; and

the application programming interface performing operations in responseto the requests that are independent of whether the requests arereceived from the first entity or the second entity.

Various example standards and protocols have been discussed. It shouldbe appreciated that this is by way of example only and other embodimentsmay use any other suitable protocol or standard.

The network interface device discussed in the application may beprovided by one or more of circuitry, hardware, and software. Likewise,the host computing device may be provided by one or more of circuitry,hardware, and software.

The applicant hereby discloses in isolation each individual featuredescribed herein and any combination of two or more such features, tothe extent that such features or combinations are capable of beingcarried out based on the present specification as a whole in the lightof the common general knowledge of a person skilled in the art,irrespective of whether such features or combinations of features solveany problems disclosed herein, and without limitation to the scope ofthe claims. The applicant indicates that aspects of the presentinvention may consist of any such individual feature or combination offeatures. In view of the foregoing description it will be evident to aperson skilled in the art that various modifications may be made withinthe scope of the invention.

1. A data processing system comprising: a host computing devicecomprising hardware resources; a network interface device arranged tocouple the host computing device to a network, the network interfacedevice comprising hardware resources; and an application configured torun on one or more of the hardware resources of the data processingsystem, wherein the data processing system is configured to selectbetween the hardware resources of the host computing device and thehardware resources of the network interface device for running at leastpart of the application.
 2. A data processing system as claimed in claim1, wherein the host computing device comprises an applicationprogramming interface configured to receive requests from theapplication to determine available hardware resources of the dataprocessing system.
 3. A data processing system as claimed in claim 1,wherein the data processing system is configured to select between thehardware resources of the network interface device and the hardwareresources of the host computing device in dependence upon at least oneof: system workload; availability of the hardware resources of the hostcomputing device; and availability of the hardware resources of thenetwork interface device.
 4. A data processing system as claimed inclaim 1, comprising a runtime support for the application, wherein theruntime support is configured to perform the selection between thehardware resources of the host computing device and the hardwareresources of the network interface device for running the application.5. A data processing system as claimed in claim 4, wherein the runtimesupport comprises a virtual machine environment.
 6. A data processingsystem as claimed in claim 1, wherein the application is configured toat least one of: form a message for transmission over the network; andconsume a message received over the network.
 7. A network interfacedevice arranged to couple the host computing device to a network, thenetwork interface device comprising first hardware resources and secondhardware resource, the network interface device comprising: anapplication configured to run on one or more of the hardware resourcesof the network interface device, wherein the network interface device isconfigured to select between the first and second hardware resources forrunning the application.
 8. A network interface device as claimed inclaim 7, wherein the application is configured to make requests to anapplication programming interface of the host computing device todetermine available hardware resources of the data processing system. 9.A network interface device as claimed in claim 7, wherein the networkinterface device is configured to select between the first hardwareresources and the second hardware resources in dependence upon at leastone of: system workload; availability of the first hardware resources;and availability of the second hardware resources.
 10. A networkinterface device as claimed in claim 7, comprising a runtime support forthe application, wherein the runtime support is configured to performthe selection between the first hardware resources and the secondhardware resources.
 11. A network interface device as claimed in claim10, wherein the runtime support comprises a virtual machine environment.12. A network interface device as claimed in claim 7, wherein theapplication is configured to at least one of: form a message fortransmission over the network; and consume a message received over thenetwork. 13-19. (canceled)
 20. A data processing system comprising: ahost computing device comprising hardware resources; a network interfacedevice arranged to couple the host computing device to a network, thenetwork interface device comprising hardware resources; and anapplication programming interface configured to receive requests from afirst entity running on the hardware of the host computing device and asecond entity running on the hardware of the network interface device,wherein operations performed by the application programming interface inresponse to the requests are independent of whether the requests arereceived from the first entity or the second entity.
 21. A dataprocessing system as claimed in claim 20, wherein the first entitycomprise a first application and the second entity comprises a secondapplication.
 22. A data processing system as claimed in claim 20,wherein the first entity and the second entity are different instancesof an application.
 23. A data processing system as claimed in claim 20,wherein the first entity and the second entity each comprise componentsof at least one runtime support.
 24. A data processing system as claimedin claim 23, wherein the requests comprise at least one of: requests foraccess to hardware resources on behalf of an application; and requestsfor an indication as to the availability of hardware resources of thedata processing system.
 25. A data processing system as claimed in claim20, wherein responses to the requests provided by the applicationprogramming interface are independent of the hardware on which the firstentity and the second entity execute. 26-30. (canceled)